Semantic Application Logging and Analytics

ABSTRACT

A system for managing dictionaries, such as an application dictionary and a domain dictionary, and for adding entries to a data log is described herein. The system may, in response to a determination that an event occurs at an application, determine that the application uses a first concept name from the application dictionary to describe the event. An entry for the event may be added to a data log for the application. The entry may also include the first concept name from the application dictionary. A mapping of the first concept name from the application dictionary to a second concept name from the domain dictionary may be generated. In some aspects, the data log may be sent to a data log analysis system capable of accessing the domain dictionary.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/296,143 filed on Jun. 4, 2014 and entitled “SEMANTIC APPLICATIONLOGGING AND ANALYTICS,” which is a continuation-in-part of U.S. patentapplication Ser. No. 13/801,286 filed on Mar. 13, 2013 and entitled“ENTERPRISE CONCEPT DEFINITION MANAGEMENT,” which claims priority toProvisional Patent App. No. 61/740,200 filed on Dec. 20, 2012 andentitled “ENTERPRISE CONCEPT DEFINITION MANAGEMENT.” U.S. patentapplication Ser. No. 14/296,143 also claims priority to ProvisionalPatent App. No. 61/955,280 filed Mar. 19, 2014 and entitled “SEMANTICAPPLICATION LOGGING AND ANALYTICS.” The entirety of each of the fouraforementioned applications is herein incorporated by reference.

TECHNICAL FIELD

Aspects described herein relates in general to electronic dictionariesand in particular to maintaining consistent definitions for entries inan electronic dictionary using a common identifier.

BACKGROUND

Enterprises such as corporations may include multiple business unitsoperating within various domains, e.g., ontologies. Each unit may seekto model the various concepts, attributes, terms, processes, and thelike within its particular domain. As part of the domain modelingprocess, a unit may define and describe the concepts relevant to itsparticular domain.

In some circumstances, a concept may be relevant to multiple unitswithin an enterprise. If each unit creates its own concept definition,then redundant and inconsistent definitions for the concepts within theenterprise may result. Accordingly, there are challenges to maintainingconsistent definitions for concepts within an enterprise that arerelevant across domains.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of aspects described herein. The summary is not anextensive overview of all aspects. It is neither intended to identifykey or critical elements nor to delineate the scope of the claims. Thefollowing summary merely presents some concepts in a simplified form asa prelude to the description below.

A computer-implemented method of managing an electronic enterpriseconcept dictionary is provided. An electronic master dictionary may bemaintained that corresponds to the enterprise concept dictionary. Themaster dictionary may include concept entries. The master dictionary mayalso include concept identifiers respectively associated with theconcept entries. The master dictionary may further include one or moreconcept definitions respectively associated with the concept entries.Electronic local dictionaries may also be maintained. A local dictionarymay include one or more of the concept identifiers included in themaster dictionary.

In response to a determination that a local dictionary includes aconcept identifier corresponding to a concept associated with a modelingcomponent, the modeling component may be associated with the conceptidentifier. In response to a determination that the local dictionarydoes not include a concept identifier corresponding to the concept, itmay be determined whether the master dictionary includes the conceptidentifier. If the master dictionary includes the concept identifier,then the concept identifier may be included in the local dictionary andassociated with the modeling component. If the master dictionary doesnot include the concept identifier, then a new concept entry may becreated in the master dictionary to obtain a new concept identifier. Thenew concept identifier may also be included in the local dictionary andassociated with the modeling component.

A system for managing an enterprise concept dictionary is also provided.An electronic master dictionary may correspond to the enterprise conceptdictionary. As noted above, the electronic master dictionary may includeconcept entries respectively associated with concept identifiers and oneor more concept definitions. Electronic local dictionaries may includeone or more of the concept identifiers included in the masterdictionary.

A dictionary management module may be in signal communication with themaster dictionary and the local dictionaries. The dictionary managementmodule may be configured to query the master dictionary for a conceptentry that corresponds to a concept associated with a modeling componentand provide a concept identifier if a concept entry is found. Thedictionary management module may also be configured to add a new conceptentry to the master dictionary and provide a new concept identifier whenthe master dictionary does not include a concept entry for the concept.A notification module may be in signal communication with the masterdictionary and may be configured to automatically provide notificationwhen a concept entry is added or updated in the master dictionary.

A non-transitory computer-readable medium is also provided. Thenon-transitory computer-readable medium may include instructions that,when executed by a processor, carry out one or more of the stepsidentified above and discussed in further detail below.

A method may comprise determining, by a computing device, that anapplication uses a first concept name from an application dictionary todescribe an event in response to a determination that the event occursat the application. An entry for the event may be added to a data logfor the application. The entry may include the first concept name fromthe application dictionary. The method may additionally comprisegenerating a mapping of the first concept name from the applicationdictionary to a second concept name from a domain dictionary. The domaindictionary may be different from the application dictionary.

Generating the mapping, as discussed above, may comprise generating amapping file that identifies the domain dictionary, the first conceptname from the application dictionary, and a concept identifier for theevent. In some aspects, the mapping file might not identify the secondconcept name from the domain dictionary. The mapping file may alsocomprise a JavaScript Object Notation for Linked Data (JSON-LD) file.The domain dictionary may also comprise a JSON-LD file. In some aspects,the domain dictionary may comprise a plurality of concept namesincluding the second concept name. Each of the plurality of conceptnames may correspond to a concept identifier. Generating the mapping mayadditionally or alternatively comprises associating the first conceptname from the application dictionary to a concept identifier, andassociating the second concept name from the domain dictionary to theconcept identifier.

The method may comprise determining, by the computing device, that theapplication uses a third concept name from the domain dictionary todescribe the second event in response to a determination that a secondevent occurs at the application. A second entry for the second event maybe added to the data log for the application, where the second entryincludes the third concept name from the domain dictionary. The data logmay also be sent to a data log analysis system capable of accessing thedomain dictionary.

A non-transitory computer-readable medium is also provided. Thenon-transitory computer-readable medium may store instructions that,when read by a computing device, cause the computing device to performone or more of the steps identified above and discussed in furtherdetail below.

An apparatus comprising a processor and memory is also provided. Thememory may store computer-executable instructions that, when executed bythe processor, cause the apparatus to perform one or more of the stepsidentified above and discussed in further detail below.

The details of these and other embodiments of the disclosure are setforth in the accompanying drawings and description below. Other featuresand advantages of aspects of the disclosure will be apparent from thedescription and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects described herein are illustrated by way of example and are notlimited by the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 is an example of an implementation of an enterprise conceptdefinition management system.

FIG. 2 is a block diagram of a system that may be used according to oneor more example embodiments of the disclosure.

FIG. 3 is a block diagram of a system for managing an electronicenterprise concept dictionary.

FIG. 4 is a flowchart of example method steps for adding new entries inan enterprise concept dictionary.

FIG. 5 is a flowchart of example method steps for automaticallyperforming a search based on a new concept entry in an enterpriseconcept dictionary.

FIG. 6 is a flowchart of example method steps for validating a newconcept entry in an enterprise concept dictionary.

FIG. 7 is a flowchart of example method steps for reviewing a newconcept entry in an enterprise concept dictionary.

FIG. 8 is a flowchart of example method steps for updating a new conceptentry in an enterprise concept dictionary.

FIG. 9 is a flowchart of example method steps for responding to anotification relating to a concept entry in an enterprise conceptdictionary.

FIG. 10 is a block diagram of an example of an enterprise conceptdictionary and examples of various domain dictionaries.

FIG. 11 is a block diagram of an example of an enterprise conceptdictionary, examples of various domain dictionaries, and examples ofvarious applications.

FIG. 12 is a block diagram of an example of a domain dictionary andexamples of various applications.

FIG. 13 is a flowchart of example method steps for generating and/orupdating concept entries in a domain dictionary and/or an applicationdictionary.

FIG. 14 illustrates block diagrams of example interactions betweenapplications and application dictionaries and/or domain dictionaries.

FIG. 15 is a flowchart of example method steps for generating a logusing one or more dictionaries.

DETAILED DESCRIPTION

The disclosure provides systems and methods for maintaining consistentconcept definitions across domains/ontologies within an enterprise. Anenterprise may be, for example, a corporation having multiple businessunits operating within respective business domains. While thedisclosures below proceed within the context of corporate enterprisesand their associated business units and business domains, it will beappreciated that aspects of the disclosure are applicable to additionalor alternative enterprises.

An enterprise may be associated with various enterprise domains such as,for example, a risk domain, a business process domain, a data domain, asecurity domain, a services domain, an application domain, and otherdomains. Enterprise engineering may involve identifying and definingcomponents to model aspects of the various domains. Such components mayinclude, for example, entities, attributes, relationships, and the like.As such, these components may be referred to as modeling components.During the domain modeling process, domain dictionaries may be createdand updated to define and describe the concepts associated with thecomponents used to model the domain. The domain dictionaries may thusinclude entries for the concepts that are associated with the componentsused to model the domain and one or more definitions for those concepts.Accordingly, an entry for a concept 104 may include a main definitionapproved for use by the various domains of the enterprise as well as alist of alternative definitions for the concept. A concept associatedwith a modeling component may be a single term or a phrase.

In some circumstances, the concepts may be relevant across domains,i.e., may be relevant to multiple domains within the enterprise.Accordingly, the concepts may be applicable to modeling components fromdifferent domains. As noted above, redundant and inconsistentdefinitions for concepts relevant across domains can result where eachdomain modeler provides a definition for a concept relevant to multipledomains. Enterprises may thus find it advantageous to maintain aconsistent definition for concepts that are relevant to multipledomains. As discussed further below, an enterprise may maintain anenterprise concept dictionary defines the concepts relevant to thedomains of the enterprise. In this way, the enterprise conceptdictionary provides a consistent definition for concepts that eachdomain may leverage when modeling the domain.

Referring to FIG. 1, an implementation of an enterprise conceptdefinition management system 100 is shown. The system 100 includes anelectronic enterprise concept dictionary 102 entries for enterpriseconcepts 104 and corresponding definitions that define and describe thesemantic meanings of the concepts. Entries for the concepts 104 in theenterprise concept dictionary 102 may include metadata related to theconcepts including, for example, a concept identifier 106 (“conceptID”), a concept name, and one or more concept definitions. The entriesfor the concepts 104 may include additional or alternative types ofmetadata. Entries for the concepts 104 in the enterprise conceptdictionary 102 may also include, for example, synonyms, pseudonyms,sources, and the like. For corporate enterprises, the enterprise conceptdictionary 102 may also be referred to as a corporate conceptdictionary. In this regard, the corporate concept dictionary serves as arepository of reference material for concepts relevant across thedomains of the corporate enterprise.

An enterprise may include various domains, and in the corporate context,a corporate enterprise may include various business domains. As shown byway of example in FIG. 1, business domains of a corporate enterprise mayinclude a business process domain 108, a data domain 110, and a securitydomain 112. The domains may include various repositories to store domainmodels created for the domains. For example, the business domain 108 mayinclude a business process repository 114 for storing business processes116 modeled within the business domain; the data domain 110 may includea data model repository 118 for storing data models 120 created withinthe data domain; and the security domain 112 may include a securitypolicy repository 122 for storing security polices 124 created withinthe security domain. One or more individuals within the enterprise maycreate and manage the models for the domains of the enterprise, e.g., abusiness process modeler 126 may model the business processes 116 of theenterprise, a data modeler 128 may model the data models 120 of theenterprise, and a security policy modeler 130 may model the securitypolicies 124 of the enterprise. In this regard, such individuals may bereferred to as domain modelers. The domain modelers 126, 128, 130 maybe, for example, employees of a corporate enterprise tasked withmanaging the respective domains 108, 110, 112.

As noted above, domain modelers may utilize various modeling componentsto model the domain. Domain modelers may maintain their own domaindictionaries that define and describe the modeling components and theconcepts associated with the modeling components. For example, abusiness process modeler 126 may maintain a business process domaindictionary 132 that includes entries for business process concepts 134;a data modeler 128 may maintain a data domain dictionary 136 thatincludes entries for data concepts 138; and a security policy modelermay maintain a security policy domain dictionary 140 that includesentries for security policy concepts 142. Entries in the domaindictionary may also include metadata, e.g., a concept ID, an componentname, an component type, an component category, and the like.

To maintain consistent definitions for concepts across domains, theentries in the domain dictionaries may be linked, related, or otherwiseassociated with respective entries for concepts 104 in the enterpriseconcept dictionary 102. As an example, an entry in a domain dictionarymay link to a concept 104 in the enterprise concept dictionary 102 viathe concept ID 106. That is, both the domain dictionary 132, 136, or 140and the enterprise concept dictionary 102 may include the concept ID 106to establish a relationship between the entry in the domain dictionaryand the entry in the enterprise concept dictionary. As a result, whenthe entry in a domain dictionary 132, 136, or 140 is referenced, thedomain dictionary may access and retrieve the definition for the concept104 from the enterprise concept dictionary 102 via the concept ID 106.In this way, the various domain dictionaries 132, 136, and 140 mayleverage consistent definitions for concepts 104. Additionally, theenterprise concept dictionary 102 remains independent of and agnostic toany domain modeling components 134, 138, 142 that leverage thedefinitions for the concept 104 of the enterprise concept dictionary102.

The corporate concept dictionary 102 thus represents a centralizedrepository for the definitions of the concepts 104. Accordingly, theenterprise concept dictionary 102 may be referred to as a masterdictionary, and a domain dictionary 132, 136, 140 may be referred to asa local dictionary. Furthermore, the enterprise concept dictionary 102and the domain dictionaries 132, 136, and 140 are electronicdictionaries and thus may be respectively referred to as an electronicmaster dictionary and electronic local dictionaries. The electronicmaster dictionary 102 and the electronic local dictionaries 132, 136,140 may be selectively implemented as, for example, a spreadsheet, adatabase with corresponding tables and columns, an XML file (eXtensibleMarkup Language), delimited value lists (e.g., comma-separated,tab-separated), or other types of electronic data stores. Accordingly,the entries in the electronic master dictionary 102 and the electroniclocal dictionaries 132, 136, and 140 may be, for example, databaserecords, line items, spreadsheet rows, and the like. The conceptidentifier 106 may be a unique identifier that uniquely identifiesentries for concepts 104 in the electronic master dictionary 102. Theconcept identifier may be, for example, a text string of alphabetic,numeric, alphanumeric, or symbolic characters as well as combinationsthereof. The concept identifier 106 may include multiple sub-parts suchas, for example, a source identifier that identifies an entity (e.g.,enterprise, organization, corporation) that created the concept, a dataidentifier that identifies the concept itself, and a version identifierthat indicates the concept version. The sub-parts may be separated by adelimiter such as a hash mark (#). As an example, the concept ID 106 mayconform to or resemble the format specified by ISO 22745-10. Associationbetween entries in the electronic master dictionary 102 and theelectronic local dictionaries 132, 136, and 140 may be established, forexample, via primary and foreign keys, via object attributes orproperties or a structured file or list, and the like. Furthermore,associating a modeling component 134, 138, or 142 with an entry for aconcept 104 in the electronic master dictionary 102 or the electroniclocal dictionaries 132, 136, and 140 may involve associating the conceptID with, including the concept ID in, or otherwise identifying theconcept ID 106 at the modeling component.

Automated tools may also retrieve the definition for a concept 104defined at the electronic master dictionary 102 using the concept ID106. Tools that may utilize the concept ID 106 to leverage the conceptdefinitions at the electronic master dictionary 102 may include, forexample, identity and access management tools for creating user roles,managing access requirements, and reviewing access rights. Notably, suchtools may include logging mechanisms that may include the concept IDs106 in log entries to accurately describe access transactions. As aresult, definitions for various information included in the log recordsis readily available during security information and event management(SIEM) analyses. Other types of tools, services, and resources utilizedby an enterprise may similarly leverage concept definitions for concepts104 using the concept ID 106.

The system 100 may be in signal communication via a computer network 144with a publicly accessible repository 146 of concept definitions, e.g.,a remote concept dictionary. The remote dictionary may be publiclyavailable via the network 144 and may thus be referred to as a publicdictionary. It will be appreciated that the remote dictionary may alsobe a remote private dictionary that is not publicly available. Theremote concept dictionary 146 may include concept definitions publishedby national and international bodies, standards organizations, orprivate entities such as corporations. In this regard, the remoteconcept dictionary 146 may include a public namespace 148 and a privatenamespace 150 for concept definitions. An enterprise may, in somecircumstances, seek to leverage the definitions published by thepublicly accessible remote concept dictionary 146 when defining theconcepts 104 in the enterprise concept dictionary 102. The enterprisemay also publish its own definitions for concepts 104 defined in itsenterprise concept dictionary 102 such that other entities may leveragethose definitions from the remote concept dictionary 146. One example ofa publicly accessible remote concept dictionary 146 is the OpenTechnical Dictionary (eOTD) maintained by the Electronic Commerce CodeManagement Association (ECCMA).

The enterprise concept dictionary 102 may be managed by an individual152 within the enterprise. Such an individual 152 may be responsible forreviewing, validating, and updating entries in the enterprise conceptdictionary 102. The individual 152 that manages the enterprise conceptdictionary 102 may be referred to as the librarian. The librarian 152may ensure data quality at the enterprise concept dictionary 102 byenforcing various standards for entries included in the enterpriseconcept dictionary. In some example embodiments, the system may beconfigured to enforce some of the standards automatically as discussedfurther below. The librarian 152 may monitor entries in the enterpriseconcept dictionary 102, e.g., the definitions proposed by domainmodelers for new concepts 104. The librarian 152 may update thedefinitions or other metadata for the concept or, additionally oralternatively, request that the domain modelers update the entries. Forexample, the librarian 152 may identify a preferred definition updatethe entry for the concept to include the preferred definition. In someinstances, the librarian 152 may determine that a definition from thepublicly accessible remote concept dictionary 146 is preferred andleverage the definition provided by the remote concept dictionary. Thelibrarian may retrieve the definition from the remote concept dictionary146 or, additionally or alternatively, link to the definition at theremote concept dictionary via the concept ID 106.

As noted above, the librarian 152 may monitor new entries for concepts104 added to the enterprise concept dictionary 102. The librarian 152may review the information provided for the new entry and accept orreject the new entry. Entries for concepts 104 in the enterprise conceptdictionary 102 may include a status, e.g., pending, approved, rejected,incomplete, and deprecated. A concept status feed 154 may be in signalcommunication with the enterprise concept dictionary 102 to notifyindividuals of the concept status and other information relating to theconcept 104, e.g., updates to the concept. Individuals within theenterprise (e.g., domain modelers) may subscribe to concepts 104 of theenterprise concept dictionary 102. The concept status feed 154 may thusprovide notifications via a feed reader (not shown) of any updates toconcepts 104 including, e.g., changes to the concept status, definition,or metadata. In this way, individuals within the enterprise mayadvantageously monitor any concepts 104 of interest.

In addition to a concept status feed 154, the concept definitionmanagement system may include an issue tracker 156 for managing theprocess of revising concept definitions. The issue tracker 156 may alsobe referred to as an issue tracking system or incident ticket system. Asdiscussed further below, issue tickets may be created at the issuetracking system and assigned to individuals within the enterprise. Theissue ticket may indicate, for example, the need to update informationfor a concept 104 at the enterprise concept dictionary 102, e.g.,provide a revised definition, provide information associated with theconcept, and so forth. The issue tracker 155 thus tracks the progress ofresolving an issue and may notify individuals of such progress.

FIG. 2 illustrates a block diagram of an enterprise concept definitionmanagement module/device 201 (e.g., a computer server) in an enterpriseconcept definition management system 200 that may be used according toan illustrative embodiment of the disclosure. The device 201 may have aprocessor 203 for controlling overall operation of the enterpriseconcept definition management module 201 and its associated components,including RAM 205, ROM 207, input/output (I/O) module 209, and memory215.

I/O 209 may include a microphone, keypad, touch screen, and/or stylusthrough which a user of the enhanced backup and retention managementmodule 201 may provide input, and may also include one or more of aspeaker for providing audio output and a video display device forproviding textual, audiovisual and/or graphical output. Software may bestored within memory 215 and/or storage to provide instructions toprocessor 203 for enabling device 201 to perform various functions. Forexample, memory 215 may store software used by the device 201, such asan operating system 217, application programs 219, and an associateddatabase 221. Processor 403 and its associated components may allow thedevice 401 to run a series of computer-readable instructions to manageenterprise concept definitions.

The server 401 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 241 and251. The terminals 241 and 251 may be personal computers or servers thatinclude many or all of the elements described above relative to thecomputing device 201. The network connections depicted in FIG. 2 includea local area network (LAN) 225 and a wide area network (WAN) 229, butmay also include other networks. When used in a LAN networkingenvironment, the server 201 is connected to the LAN 225 through anetwork interface or adapter 223. When used in a WAN networkingenvironment, the server 201 may include a modem 227 or other means forestablishing communications over the WAN 229, such as the Internet 231.It will be appreciated that the network connections shown areillustrative and other means of establishing a communications linkbetween the computers may be used. The existence of any of variouswell-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like ispresumed.

Additionally, an application program 219 used by the enterprise conceptdefinition management module 201 according to an illustrative embodimentof the disclosure may include computer executable instructions forinvoking functionality related to managing enterprise conceptdefinitions. Enterprise concept definition management module 201 and/orterminals 241 or 251 may also be mobile terminals, such as smart phones,personal digital assistants (PDAs), and the like including various othercomponents, such as a battery, speaker, and antennas (not shown).

The disclosure is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the disclosure include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, and distributed computingenvironments that include any of the above systems or devices, and thelike.

The disclosure may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include routines,programs, objects, components, data structures, and the like thatperform particular tasks or implement particular abstract data types.The disclosure may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked, for example, through a communications network. In adistributed computing environment, program modules may be located inboth local and remote computer storage media including memory storagedevices.

Referring to FIG. 3, an example of an implementation of a system 300 formanaging an enterprise concept dictionary is shown. As discussed above,the system may include an electronic master dictionary 302 and one ormore electronic local dictionaries 304. As noted above, the masterdictionary may correspond to the enterprise concept dictionary for anenterprise and the local dictionaries may respectively correspond todomain dictionaries for the various domains of the enterprise.

The master dictionary 302 and the local dictionary 304 may each includeconcept entries 306 and 308 for concepts relevant to an enterprise. Theconcept entries 306 at the master dictionary 302 may include a conceptID 310. The concept ID 310 may be included in one or more conceptentries 308 of a local dictionary 304. The concept entries 306 in themaster dictionary 302 may include one or more definitions 312. Thedefinitions for a concept entry 306 at the master dictionary 302 mayinclude, for example, a main definition and one or more alternativedefinitions. A concept entry 306 at the master dictionary 302 may alsoinclude one or more synonyms 314 for the concept, one or more sources316 for the definitions 312 of the concept, and a status 318 for theconcept. A concept entry 306 at the master dictionary may additionallyinclude a data quality specification 320 the concept entry 306 mustsatisfy. Additionally, a concept entry 306 at the master dictionary mayinclude a list of subscribers 322 as well as one or more concept IDs 324for other concept entries that are related to the concept.

A concept entry 308 at the local dictionary 304 may include metadata 326for the concept. The metadata 326 may include, for example, a conceptname, type, and category. It will be appreciated that, in some exampleembodiments, the master dictionary 302 may include the metadata 326. Asseen in FIG. 3 and as explained above, concept entries 308 in the localdictionary 304 may be linked to concept entries 306 in the masterdictionary 302 via the concept ID 310. In this way, the local dictionary304 may leverage the definitions 312 for a concept from the masterdictionary 302, and the master dictionary may provide consistentdefinitions to various domains of an enterprise.

A domain modeler may utilize a modeling tool 328 to develop andenterprise model 330 for a domain of the enterprise. A modeling tool maybe, for example, commercially available tools to develop databaseschemas, design software systems, model business processes and the like.As noted above, such modeling tools 328 may provide various modelingcomponents 332 for modeling the various enterprise domains. A modelingcomponent 332 may include, be associated with, or otherwise identify aconcept ID 310 such that a definition for the concept associated withthe modeling component may be retrieved from the master dictionary 302.

The system 300 may also include a dictionary management module 334 insignal communication with the master dictionary 302 and the localdictionaries 304. The dictionary management module 334 may be a softwareapplication, service, or process (or set of software applications,services, and processes) configured to facilitate the process ofmanaging the respective concept entries 306 and 308 at the masterdictionary 302 and the local dictionaries 304. For example, thedictionary management module 334 may be configured to: automaticallysearch a local dictionary for a concept; automatically search the masterdictionary for a concept; provide new concept IDs 310 for new conceptentries 306 or 308; facilitate creating, reviewing, and updatingrespective concept entries; and facilitate validation of new conceptentries. These processes will be discussed in further detail below. Thedictionary management module may provide various user interface screensat a terminal 336 that enable a domain modeler or a librarian to add,update, and review concept entries 306 or 308 at the master dictionary302 or the local dictionaries 304. Accordingly, the dictionarymanagement module may be implemented as a web-enabled interface,standalone desktop application, mobile application, and the like.

As seen in FIG. 3, the dictionary management module may be in signalcommunication with a public dictionary 338 via a network 340. Asmentioned above, the public dictionary may also include concept entries342 having a concept ID 344 and one or more definitions 346 for theconcept. As discussed further below, the dictionary management module334 may be configured to automatically initiate a search of the publicdictionary 338 for a concept associated with a concept entry 306 at themaster dictionary 302.

The system 300 may also include a notification module 348 configured toprovide notifications relating to the respective concept entries 306 and308 at the master dictionary 302 and the local dictionaries 304. Thenotification module 348 may be configured to monitor the masterdictionary 302 and the local dictionaries 304 and provide notificationsin response to events occurring at the master dictionary or a localdictionary, e.g., in response to creation of or updates to conceptentries 306 or 308. Such notifications may include for example: anotification that a new concept entry 306 has been added to the masterdictionary 302; a notification that a concept entry has been updated; anotification that a concept status 318 has changed; and a notificationof a task to complete for a concept entry. It will be appreciated withthe benefit of this disclosure that the notification module may provideadditional or alternative notifications. In some example embodiments,the master dictionary may be configured to broadcast changes to thenotification module, which may in turn provide the notifications to theindividuals.

The notification module may include, for example, an email messagingsystem, an issue tracking system, a web feed system (e.g., RSS), andcombinations thereof. Notifications may also be provided at one or moreof the interface displays provided by the dictionary management module.Accordingly, notifications may be provided as email messages, issuetickets, content items of a web feed, messages at an interface display,and combinations of such. It will be appreciated that the notificationmodule may provide additional or alternative types of notificationsusing additional or alternative approaches. Such notifications may bepresented to a librarian, domain modeler, or other individual of theenterprise at a terminal 336.

Regarding the web feed, the system may, in some example implementations,publish multiple web feeds. As an example, the system may publish a mainweb feed that provides notification of changes to all concept entries inthe master dictionary, a set of web feeds that provide notification ofchanges to concept entries of a particular concept type or related to aparticular domain (e.g., a security policy web feed, a risk policy webfeed, a business process domain web feed, a data domain web feed, andthe like), or, additionally or alternatively, individual web feeds foreach concept entry in the master dictionary. Individual may subscribe toone or more of the web feeds, e.g., the web feeds for concepts, concepttypes, or domains the individual is interested in. Subscribers may viewthe web feeds at a web feed reader or web feed aggregator.

Referring to FIG. 4, a flowchart 400 of example method steps for addingnew entries in the enterprise concept dictionary is shown. A domainmodeler may identify a concept associated with a modeling component fora domain (block 402). The domain modeler may then determine whether adefinition for the concept exists by querying the local dictionary forthe concept (block 404). The domain modeler may, for example, providethe name of the concept to the dictionary management module, which maysearch the local dictionary for a concept entry corresponding to theconcept name provided. If the local dictionary includes a concept entryfor the concept (block 406), then the dictionary management module mayprovide the concept ID of the concept entry such that the domainmodeling component may be associated with the concept entry at the localdictionary corresponding to the concept ID (block 408). As noted abovethe concept ID may be associated with, included in, or otherwiseidentified at the modeling component. If the local dictionary does notinclude a concept entry for the concept (block 406), then the dictionarymanagement module may automatically search the master dictionary for aconcept entry provided (block 410). If the master dictionary includes aconcept entry for the concept (block 412), then the dictionarymanagement module may obtain the concept ID from the master dictionaryand add an entry in the local dictionary for the concept (block 414).The dictionary management module may configure the new concept entry inthe local dictionary to include the concept ID for the concept such thatthe new concept entry at the local dictionary is associated with theconcept entry for the concept at the master dictionary. The domainmodeling component may in turn be configured to include or identify theconcept ID such that the domain modeling component is associated withthe concept entry at the local dictionary corresponding to the conceptID (block 408).

If the master dictionary does not include a concept entry correspondingto the concept (block 412), then the domain modeler may add a newconcept entry to the master dictionary (e.g., a master concept databaserecord) for the concept (block 416). Upon creation of the new conceptentry, the dictionary management module may generate a new concept IDfor the new concept entry (block 418). The domain modeler may theninitialize the new concept entry (block 420) by providing, e.g., aconcept name and a proposed definition. Additionally, initialization ofthe new concept entry may include setting the status of the new conceptentry to “pending” to indicate that the new concept entry has not yetbeen reviewed and approved. The dictionary management module mayfacilitate creation and configuration of the new concept entry at themaster dictionary by providing one or more display interfaces at whichthe domain modeler may provide the concept information. After creationof the new concept entry in the master dictionary, the dictionarymanagement module may obtain the new concept ID and add a new entry forthe concept in the local dictionary (e.g. a local concept databaserecord) that includes the new concept ID (block 414). The new concept IDis thus available to the domain modeler for use with the domain modelingcomponent.

In some example embodiments, the dictionary management module may beconfigured to validate new concept entries upon creation (block 422).Validating a new concept entry may include, for example, ensuring thatthe new concept entry includes an initial proposed definition, ensuringthat the new concept entry satisfies any data quality specifications forthe concept type, and the like. Validating new concept entries will bediscussed in further detail below. Additionally, in some exampleembodiments, the dictionary management module may automaticallysubscribe the domain modeler to the new concept entry (block 424) suchthat a notification module may notify the domain modeler of any changesor updates to the concept entry.

The notification module may determine that a new concept entry has beenadded to the master dictionary and automatically notify a librarian thatthe domain modeler has added the new concept entry (block 426). As notedabove, the notification module may notify the librarian via an emailmessage, an issue ticket, or a message displayed at a display interface.For example, the display interface may include a list of all newconcepts that domain modelers of an enterprise have added. The librarianmay thus proceed through the list review the new concept entries andeither approve or reject the new concept entries. As discussed furtherbelow, the librarian may update concept entries during review or mayrequest that a domain modeler to update the concept entry.

Accordingly, it will be appreciated that the enterprise dictionarymanagement system permits domain modelers to create new concept entriesas needed during domain modeling activities. The system permits domainmodelers to expand an enterprise concept dictionary with new concepts asneeded and provides the domain modelers with concept IDs that can beused in the domain model upon creation of the concept entry. In thisway, domain modelers are not hindered in their domain modeling effortsby waiting for approval of the new concept entries. Instead, review ofthe new concept entries may advantageously take place simultaneouslywith the use of such concept entries at the domain modeling level.Additionally, any updates to the concept entries will be automaticallyreflected at the domain model via the concept ID that references andlinks to the concept entry at the enterprise concept dictionary.

In some example implementations the dictionary management module may beconfigured to automatically search one or more remote dictionaries fordefinitions of a new concept added to the master dictionary of anenterprise. FIG. 5 is a flowchart 500 of example method steps forautomatically performing a search based on a new concept entry in theenterprise concept dictionary. A new concept entry may be added to themaster dictionary (block 502). During the creation process (e.g., duringinitialization) the dictionary management module may automaticallyinitiate a search query for the concept (block 504). The search querymay include, e.g., the concept name and may conform to a formatspecified by an application programming interface (API) provided by aremote dictionary, e.g., a public dictionary accessible via a network.

The dictionary management module may transmit the search query to theremote dictionary, e.g., via the network (block 506). If the remotedictionary does not include any definitions for the concept (block 508),then the dictionary management module may conclude the search (block510). If, however, the remote dictionary does include a definition forthe concept (block 508), then the remote dictionary may provide one ormore definitions of the concept to the dictionary management module(block 512). The remote dictionary may provide the definitions via thenetwork in, e.g., one or more responses to the search query. Uponreceipt of the definitions from the remote dictionary, the dictionarymanagement module may add one or more of the definitions received to thelist of alternative definitions of the new concept entry in the masterdictionary (block 514). The list of alternative definitions, which mayinclude the definitions received from the remote dictionary, may thus bepresented to the librarian during the review of the new concept entry(block 516).

As noted above, the dictionary management module may be configured tovalidate a new concept entry upon creation. FIG. 6 is a flowchart 600 ofexample method steps for validating a new concept entry in the masterdictionary. A new concept entry may be created at the master dictionary(block 602). A domain modeler may provide concept information for theconcept, e.g., metadata such as the concept name, a concept type, and aconcept type (block 604). A new concept identifier may be generated andset for the new concept entry. The domain modeler may also provide aninitial proposed concept definition for the new concept entry (block606).

As noted above, validating the new concept entry may include determiningwhether one or more data quality specifications are satisfied. In someexample embodiments, concept entries may be associated with or specify aparticular concept type. The concept type may in turn be associated withone or more data quality specifications. Accordingly, when a new conceptentry is added to the master dictionary, the dictionary managementmodule may determine whether the concept type of the new concept entryis associated with or includes data quality specifications (block 608).If data quality specifications are not specified for the concept type ofthe new concept entry (block 610), then the dictionary management modulemay continue with initialization (block 612), and the notificationmodule may provide notification of the new concept entry onceinitialization is complete (block 614).

If data quality specifications are specified for the concept type of thenew concept entry (block 610), then the dictionary management module maydetermine whether the data quality specifications are satisfied (block616). Data quality specifications may be based on external governance orindustry standards or, additionally or alternatively, on internalenterprise standards. Data quality specifications may specify, forexample, certain types of information that the concept entry in themaster dictionary must include. For example, a general data qualityspecification may specify that a concept entry at the master dictionarymust include at least one definition. If, in this example, thedictionary management module determines that a concept entry does notinclude a definition, the dictionary management module may determinethat the concept entry does not satisfy the data quality specifications.Data quality specifications may also specify relationships that shouldbe established between a concept entry of a particular concept type andother concept entries in the master dictionary. As another example, dataquality specifications in the business domain may specify that conceptentries relating to business processes should be associated with atleast one concept entry relating to a job function. Accordingly, if, inthis example, the dictionary management module determines that abusiness process-type concept entry is not associated with at least onejob function-type concept entry, then the dictionary management modulemay determine that the concept entry does not satisfy the data qualityspecifications associated with the business process concept type. Itwill be appreciated that additional or alternative data qualityspecifications may be selectively employed.

If the dictionary management module determines that a new concept entrydoes not satisfy one or more associated data quality specifications(block 616), then the dictionary management module may set the status ofthe new concept entry as, e.g., “incomplete” (block 618). In someexample embodiments, the dictionary management module may be configuredto initiate notification to an individual (e.g., a librarian or domainmodeler) that the new concept entry is incomplete. As noted above, thenotification module may be (or include) an issue tracker. Accordingly,in some example embodiments, the dictionary management module mayautomatically create a new issue ticket in the issue tracker andidentify or otherwise associate the new issue ticket with the newconcept entry (block 620). The dictionary management module may alsoindicate in the new issue ticket one or more tasks that an individualmust carry out with respect to the new concept entry, e.g., provide adefinition, establish appropriate relationships with other conceptentries, and the like. The dictionary management module mayautomatically assign the issue ticket to an individual responsible forresponding to the issue ticket (block 622). The notification module,e.g., the issue tracker may thus provide notification to the individualof the new issue ticket assigned (block 624). As noted above, however,because the new concept entry has been created, the concept entry andcorresponding concept ID are thus available as needed for domainmodeling efforts. An individual may respond to the issue ticket asdesired independently of any domain modeling efforts. It will beappreciated that the individual assigned to the issue ticket may or maynot be the individual that created the new concept entry. Onceinitialization of the new concept entry is finished, whether the newconcept entry is complete or incomplete, the notification module maynotify the librarian that a new concept entry has been added to themaster dictionary (block 614). In some example embodiments, thenotification to the librarian may indicate whether the new concept entryis complete or incomplete.

As also noted above, a librarian may review new concept entries added tothe master dictionary. The librarian may review the new concept entriesto ensure, for example, that the proposed definition is acceptable forthe enterprise. Referring to FIG. 7, a flowchart 700 of example methodsteps for reviewing a new concept entry in a master dictionary is shown.As shown above, a new concept entry may be added to a master dictionaryof an enterprise (block 702), and a notification module mayautomatically notify a librarian of the new concept entry (block 704).The dictionary management module may present one or more user interfacedisplays to the librarian (e.g., at a web portal or desktop application)that permit the librarian to manage the master dictionary of theenterprise. One of the user display interfaces that the dictionarymanagement module may present to the librarian may be referred to as amaster dictionary management interface (block 706).

The master dictionary management interface may provide the librarianwith access to the master dictionary of the enterprise. The librarianmay select a concept entry at the master dictionary to view theinformation associated with the selected concept entry, e.g., theconcept definition, the list of alternative definitions, the list ofsources for the definition, the status of the definition and so forth.The master dictionary management interface may also present a list ofrecently added concept entries for the librarian to review (block 708).The librarian may select one of the new concept entries (block 710), andthe dictionary management module may retrieve and present theinformation for the selected concept (block 712), e.g., the proposeddefinition, the concept type, timestamp information indicating when theconcept was created, and the domain modeler that created the concept.

As described above, the dictionary management module may be configuredto automatically search for public definitions of the concept at apublicly available remote dictionary. If the dictionary managementmodule located any publicly available definitions for the concept (block714), then the dictionary management module may display a list ofalternative definitions for the concept (block 716) for the librarian toconsider.

The librarian may review the information for a selected concept entry(block 718) including, for example, the definition, the metadata, thelist of alternative definitions. If the librarian considers the conceptinformation to be satisfactory (block 720), then the librarian mayupdate the status of the concept to, e.g., “approved” (block 722). Thenotification module may detect the change to the status of the conceptentry and notify one or more subscribers to the concept entry of thechange (block 724). As noted above, a concept entry may include a listof subscribers, which may be, for example, a list of email addresses, alist of employee numbers, or a list of other information used toidentify individual that requested to be notified when changes to theconcept entry occur. As also noted above, notification may be providedas an email message, an issue ticket, publications to a web feed, andthe like.

If the librarian determines that the concept information is notsatisfactory (block 720), the librarian may update the concept statusto, e.g., “rejected” (block 726). The librarian may then create in issueticket for the concept entry (block 728) and indicate at the issueticket why the concept entry was rejected. The librarian may reject theconcept entry where, for example, the librarian determines the proposeddefinition is incomplete or insufficient. The librarian may assign theissue ticket to an individual (block 730) such that the individual isnotified the concept entry needs updating. In some examples, thelibrarian may assign the issue ticket to the domain modeler thatoriginally created the concept entry. The issue tracker may thus providenotification of the new issue ticket for the concept entry (block 732).In this way, the librarian may advantageously manage the masterdictionary from a centralized location, delegate tasks to domainmodelers where updates are needed to the concept entries in theenterprise concept dictionary, and monitor the progress of such updatesas they are addressed.

In FIG. 8, another flowchart 800 of example method steps for updating aconcept entry in a master dictionary is shown. In FIG. 8, the librarianperforms the update rather than assigning a task to an individual asshown by way of example in FIG. 7. In FIG. 8, the librarian may select aconcept entry of the master dictionary at the master dictionarymanagement interface (block 802), and review the concept information(e.g., the definition) for the selected concept (block 804). If theconcept information for the selected concept is satisfactory (block806), then the librarian may update the concept status to, e.g.,“approved” (block 808), and the notification module may notify thesubscribers to the concept of the status change (block 810).

If the concept information for the selected concept is not satisfactory(block 808), then the librarian may review the list of alternativedefinitions for the selected concept (block 812). If one of thealternative definitions for the selected concept is satisfactory (block814), then the librarian may select a desired alternative definition asthe main definition for the concept entry (block 816). If the librariandoes not find any of the alternative definitions for the conceptsatisfactory (block 814), the librarian may provide new definition forthe concept entry based on the proposed definition or one or more of thealternative definitions. Having updated the definition for the conceptentry, the librarian may update the concept status to, e.g., “approved”(block 808), and the notification module may notify the subscribers tothe concept of the new definition (block 810).

In FIG. 9, a flowchart 900 of example method steps for responding to anotification from the notification module is shown. An individual, e.g.,a data modeler may receive an issue ticket associated with a conceptentry (block 902). As noted above, the issue ticket may identify a taskfor the data modeler to complete with respect to the concept entry,e.g., revising the definition, completing the definition, or ensuringdata quality specifications associated with the concept entry aresatisfied. The data modeler may review the concept entry identified bythe issue ticket (block 904) including, e.g., the concept definition.

In some examples, the issue ticket may have been created because thelibrarian rejected the proposed definition for the concept (block 906).Accordingly, the data modeler may revise the concept definition (block908) in response. In other examples, the issue ticket may have beencreated because one or more data quality specifications associated withthe concept entry is not satisfied (block 910). In response, the datamodeler may update the concept entry to satisfy the associated dataquality specifications (block 912). Once the data modeler has updatedthe concept entry to resolve the issues identified in the issue ticket(block 914), the notification module may provide notification to thelibrarian indicating the concept entry has been updated (block 916).

In response to the notification, the librarian may review the changes(block 918) and determine whether the revised concept information issatisfactory. If the revised concept information is satisfactory (block920), then the librarian may update the concept status to, e.g.,“approved” (block 922), and the notification module may notify thedomain modeler of the status change (block 924). If the librariandetermines that the revised concept information is not satisfactory(block 920), then the librarian may repeat the process by creating a newissue ticket for the concept entry (block 926), assign the new issueticket to the domain modeler (block 928), and provide notification tothe domain modeler of the new issue ticket via the notification module(block 930).

The dictionary management module may provide a dictionary managementinterface that domain modelers may use to view the local dictionaries(e.g., the domain dictionaries) as well as the master dictionary (e.g.,the enterprise concept dictionary). The dictionary management interfacemay present the notifications provided by the notification module, e.g.,the issue tickets or web feeds. A domain modeler may select a conceptentry to review or update, e.g., revise the concept definition, updateassociated concepts, and so forth.

Referring now to FIG. 10, a block diagram of an example of an enterpriseconcept dictionary 1000 and various domain dictionaries 1002, 1004, 1006is shown. As seen in FIG. 10, a concept identifier 1008 links a concept1010 in the enterprise concept dictionary 1000 to attributes 1012, 1014,1016 in respective domain dictionaries 1002, 1004, 1006. The concept1010 in the enterprise concept dictionary 1000 may include or otherwisebe associated with the concept ID 1008. The respective attributes 1012,1014, 1016 in each domain dictionary 1002, 1004, 1006 may also includeor otherwise be associated with the concept ID 1008. In this way, theconcept ID 1008 links domain attributes 1012, 1014, 1016 to a commonconcept 1010 in the enterprise concept dictionary 1002. The domainattributes 1012, 1014, 1016 may thus reference and leverage the conceptdefinition for the enterprise concept 1010 identified by the concept ID1008.

In some aspects, a computer-implemented method may comprise maintainingan electronic master dictionary that corresponds to an electronicenterprise concept dictionary and includes one or more concept entries,one or more concept identifiers respectively associated with the one ormore concept entries, and one or more concept definitions respectivelyassociated with the one or more concept entries. The method may includemaintaining an electronic local dictionary wherein the local dictionaryincludes one or more of the concept identifiers included in the masterdictionary. The method may include determining whether the localdictionary includes a concept identifier corresponding to a conceptassociated with a modeling component. The method may include associatingthe modeling component with the concept identifier in response to adetermination that the local dictionary includes the concept identifier.The method may include determining whether the master dictionaryincludes the concept identifier in response to a determination that thelocal dictionary does not include the concept identifier. The method mayinclude including the concept identifier in the local dictionary andassociating the modeling component with the concept identifier inresponse to a determination that the master dictionary includes theconcept identifier. The method may also include creating a new conceptentry for the concept in the master dictionary to obtain a new conceptidentifier, including the new concept identifier in the localdictionary, and associating the modeling component with the new conceptidentifier in response to a determination that the master dictionarydoes not include the concept identifier.

In some aspects, the master dictionary may include a status associatedwith the new concept entry. The method may further include setting thestatus to indicate that approval of the new concept entry is pending andautomatically providing notification that indicates the new conceptentry has been created in the master dictionary.

In some aspects, the method may further comprise determining that thenew concept entry has not been approved, updating the status associatedwith the new concept entry to indicate that the new concept entry hasnot been approved, and automatically providing notification thatindicates the new concept entry has not been approved.

In some aspects, the method may further comprise creating a new issueticket in an issue tracking system wherein the issue ticket indicatesone or more reasons that the new concept entry was not approved,associating the issue ticket with the new concept entry, and associatingthe issue ticket with an individual responsible for updating the newconcept entry.

In some aspects, the method may further comprise initiating a searchquery for the concept associated with the new concept entry at a publicdictionary, determining whether the public dictionary includes one ormore public definitions for the concept associated with the new conceptentry, and including one or more of the public definitions for theconcept in the master dictionary such that the one or more publicdefinitions are associated with the new concept entry.

In some aspects, the master dictionary may include a concept definitionassociated with the new concept entry. The method may further comprisereceiving user input corresponding to a selection of one of the publicdefinitions associated with the new concept entry, and setting theconcept definition for the new concept entry to the public definitionselected.

In some aspects, the method may include updating concept informationassociated with one of the concept entries included in the masterdictionary, and automatically providing notification that the conceptentry has been updated.

In some aspects, automatically providing notification that one of theconcept entries in the master dictionary has been updated may includepublishing update information associated with the concept entry to a webfeed associated with the concept entry such that one or more subscribersto the web feed receive the update information.

In some aspects, the master dictionary may include a list of one or moresubscribers that subscribe to the concept entry. The step ofautomatically providing notification that one of the concept entries inthe master database has been updated may include creating an issueticket in an issue tracking system wherein the issue ticket includes theconcept information that has been updated, and associating the issueticket with one or more of the subscribers that subscribe to the conceptentry.

In some aspects, the local dictionary includes metadata respectivelyassociated with one or more of the concept identifiers included in thelocal dictionary, and the metadata may include at least one of a conceptname, a concept type, a concept category, and combinations thereof.

In some aspects, a system may comprise an electronic master dictionarythat corresponds to an enterprise concept dictionary and includes one ormore concept entries, one or more concept identifiers respectivelyassociated with the one or more concept entries, and one or more conceptdefinitions respectively associated with the one or more conceptentries. The system may also include an electronic local dictionary,wherein the local dictionary includes one or more of the conceptidentifiers included in the master dictionary. In some aspects, adictionary management module may be in signal communication with themaster dictionary and the local dictionary. Furthermore, the dictionarymanagement module may be configured to query the master dictionary for aconcept entry that corresponds to a concept associated with a modelingcomponent, provide a concept identifier for the concept entry when themaster dictionary includes the concept entry for the concept, and add anew concept entry to the master dictionary and provide a new conceptidentifier associated with the new concept entry when the masterdictionary does not include the concept entry for the concept. Thesystem may also comprise a notification module in signal communicationwith the master dictionary, and the notification module may beconfigured to automatically provide notification when the new conceptentry is added to the master dictionary and when one of the conceptentries in the master dictionary is updated.

In some aspects, the master dictionary may be further configured toautomatically initiate a search for the concept associated with the newconcept entry at a public dictionary, retrieve one or more publicdefinitions for the concept included in the public dictionary, andinclude the one or more public definitions for the concept in the masterdictionary such that the one or more public definitions are associatedwith the new concept entry.

In some aspects, the master dictionary may include concept entries for aplurality of enterprise domains, the electronic local dictionary may beone of a plurality of electronic local dictionaries, and individuallocal dictionaries of the plurality of local dictionaries mayrespectively correspond to one of the enterprise domains of theplurality of enterprise domains.

In some aspects, the system may further comprise a web feed in signalcommunication with the notification module. The notification module maypublish updates to concept information associated with one of theconcept entries included in the master dictionary via the web feed.

In some aspects, the system may further comprise an issue tracker insignal communication with the dictionary management module. Thedictionary management module may be further configured to create anissue ticket at the issue tracker, associate one of the concept entriesincluded in the master dictionary with the issue ticket, indicate in theissue ticket a task relating to the concept entry, and associate theissue ticket with an individual responsible for completing the task.

In some aspects, a non-transitory computer-readable medium havingcomputer-executable instructions stored thereon that, when executed by aprocessor, may cause the processor to determine whether a localdictionary database includes a concept identifier corresponding to aconcept associated with a modeling component, associate the modelingcomponent with the concept identifier in response to a determinationthat the local dictionary database the concept identifier, determinewhether a master dictionary database includes the concept identifier inresponse to a determination that the local dictionary database does notinclude the concept identifier, create a new local concept record forthe concept identifier in the local dictionary database and associatingthe modeling component with the concept identifier in response to adetermination that the master dictionary database includes the conceptidentifier, and create a new master concept record for the concept inthe master dictionary database to obtain a new concept identifier, a newlocal concept record for the new concept identifier in the localdictionary database, and associating the modeling component with the newconcept identifier in response to a determination that the masterdictionary database does not include the concept identifier.

In some aspects, the concept may be associated with a concept type andwherein the computer-executable instructions, when executed by theprocessor, may cause the processor to determine whether one or more dataquality specifications are associated with the concept type associatedwith the concept. In response to a determination that one or more dataquality requirements are associated with the concept type, the processormay determine whether the new master concept record for the conceptsatisfies one or more of the data quality specifications. In response toa determination that the new master concept record does not satisfy atleast one of the data quality specifications, the processor may set astatus associated with the new master concept record to indicate thatthe new master concept record is incomplete.

In some aspects, the computer-executable instructions, when executed bythe processor, may cause the processor to automatically providenotification that the new master concept record is incomplete inresponse to the determination that the new master concept record doesnot satisfy at least one of the data quality specifications.

In some aspects, providing notification that the new master conceptrecord is incomplete may include automatically creating an issue ticketin an issue tracking system wherein the issue ticket indicates one ormore of the data quality specifications the new master concept recorddoes not satisfy, automatically associating the issue ticket with thenew master concept record, and automatically associating the issueticket with an individual responsible for updating the new masterconcept record.

In some aspects, the computer-executable instructions, when executed bythe processor, may cause the processor to determine that the new masterconcept record has been updated, and automatically providingnotification indicating that the new master concept record has beenupdated to an individual responsible for reviewing the new masterconcept record.

FIG. 11 is a block diagram of an example of an enterprise conceptdictionary, examples of various domain dictionaries, and examples ofvarious applications. In some aspects, the enterprise concept dictionary1100 may be the enterprise concept dictionary previously described. Forexample, the enterprise concept dictionary 1100 may link, relate, orotherwise associate concepts in domain dictionaries to concepts in theenterprise concept dictionary 1100. In some aspects, the enterpriseconcept dictionary 1100 might not link, relate, or otherwise associatedomain concepts with enterprise concepts. For example, the enterpriseconcept dictionary 1100 might be a collection of concepts or attributesused by a plurality of domain dictionaries, without linking, relating,or otherwise associating the domain concepts or attributes to otherdomain concepts or attributes or enterprise concepts or attributes. Insome aspects, the enterprise concept dictionary 1100 might be a singlerepository or storage location, such as a federated registry.

Four domain dictionaries are illustrated in FIG. 11, a Domain Dictionary1 1105, a Domain Dictionary 2 1110, a Domain Dictionary 3 1115, and aDomain Dictionary N 1120. One of ordinary skill in the art wouldrecognize that any number of domain dictionaries may exist. Aspreviously described, each domain dictionary may correspond to aparticular domain, such as a business domain. One or more applicationsmay be associated with each domain dictionary. These applications mayrun on each domain or otherwise communicate with (or otherwise haveaccess to) their respective domain dictionary. For example, ApplicationA 1125, Application B 1130, Application C 1135, Application D 1140,Application E 1145, and Application F 1150 may be associated with DomainDictionary 1 1105. Application G 1155 may be associated with DomainDictionary 2 1110 and Domain Dictionary 3 1115. Application H 1160 andApplication J 1165 may each be associated with Domain Dictionary 3 1115.Application K 1170 and Application L 1175 may each be associated withDomain Dictionary N 1120.

Each application might have its own application dictionary thatidentifies and defines one or more concepts, similar to the enterpriseconcept dictionary and/or domain dictionaries previously described. Insome aspects, a concept or term in an application dictionary may belinked, related to, or otherwise associated with a concept or term in adomain dictionary. Some applications might not have their owndictionaries. For example, Application B 1130 and Application H 1160might not have dictionaries. Instead, Application B and Application Hmight utilize one or more domain dictionary for concepts and terms, aswill be described in further detail in the examples below. Anapplication may comprise, for example, an operating system, a database,an enterprise application, a mobile application, a network device,and/or any other software or hardware component.

Applications may be configured to generate one or more logs, such as adata log file. Data logs may include information identifying, forexample, actions taken by users, the user(s) taking each action, errorsoccurring during execution of actions in the application, date and/ortime information for each action, and performance statistics of theapplication, among numerous other types of information. For example, alog might indicate that an application shut down too quickly or did notopen. Logs may be formatted differently for each application or type ofapplication. For example, an operating system may format a data logdifferently from a database. Logs may also use different concepts orterms for the information included in each log. For example, oneapplication may use the concept name “Party Identifier” for the partyidentifier of a customer of an institution, such as a financialinstitution. On the other hand, a different application may use theconcept name “Party_ID” for the party identifier of a customer. As willbe discussed in further detail in the examples that follow, concepts inapplication dictionaries, mapping dictionaries, and/or domaindictionaries may be linked, related to, or otherwise associated withconcepts in another dictionary.

FIG. 12 is a block diagram of an example of a domain dictionary 1 1205and examples of various applications associated with the domaindictionary, including Application A 1225, Application B 1230,Application C 1235, Application D 1240, Application E 1245, andApplication F 1250. Domain dictionary 1 1205 might define a concept“PartyID” for the party identifier of a customer of an institution. Insome aspects, “PartyID” may be the common term (e.g., proper term orcanonical term) used by the particular business domain. Application A1225 might use concepts from its own dictionary in addition to (orinstead of) concepts from the domain dictionary 1 1205. For example,application A 1225 might use the term “Party Identifier” from its owndictionary, instead of the term “PartyID” from the domain dictionary.Application B 1230, on the other hand, might use the concepts from thedomain dictionary 1 1205 (e.g., “PartyID”). If application B 1230 doesnot use any of its own concept names, it might not have its ownapplication dictionary. Application C 1235 may use the term “Party_ID”from its own application dictionary, instead of the term “PartyID” fromthe domain dictionary. Similarly, application D 1240 may use the term“Party_ID” from its own application dictionary; application E 1245 mayuse the term “PARTY_ID” from its own application dictionary; applicationF 1250 may use the term “partyID” from its own application dictionary.As will be discussed in further detail in the examples that follow, eachof the terms “Party Identifier,” “Party ID,” “Party_ID,” “PARTY_ID,” and“partyID” used by the applications may be mapped to the common (e.g.,canonical) term “PartyID” used by the business domain.

FIG. 13 is a flowchart of example method steps for generating and/orupdating concept entries in a domain dictionary and/or an applicationdictionary. In step 1302, a computing device may receive a name for aconcept. For example, a user (such as the librarian, modeler, or anyother user) may input the concept name via a graphical user interface.Additionally or alternatively, an application may provide the conceptname. The concept name may be, for example, “PartyID.” In step 1304, thecomputing device may determine whether the received concept name is anupdate to a concept existing, for example, in the domain dictionary. Thecomputing device may make this determination based on the unique conceptID associated with the received concept name, as previously discussed.For example, the concept name “PartyID” might be stored in associationwith a concept ID “XXXX32,” which may be used to determine whether theconcept already exists in the domain dictionary.

If the concept name is an update to an existing concept (step 1304:Yes), the computing device may update the concept name for the existingconcept ID in step 1306. For example, assume that the existing conceptname for the party identifier identifying a customer is“PartyIDENTIFIER.” A user (or application) may provide “PartyID” for theconcept ID XXXX32, indicating that the user desires to change theconcept name for concept ID XXXX32 from “PartyIDENTIFIER” to “PartyID.”When the computing device receives the new concept name “PartyID,” thecomputing device may update the domain dictionary with the new conceptname “PartyID” in step 1306.

If the concept name is not an update to an existing concept (step 1304:No), the computing device may determine that the concept is new andproceed to create a new entry for the domain dictionary. The computingdevice may make this determination if the user inputs a concept namethat is not associated with a concept ID. In step 1308, the computingdevice may generate a concept ID for the new concept. For example, thegenerated concept ID might be XXXX32 or in any other format, aspreviously discussed. The concept ID may be unique to that concept andbe automatically generated by a software program or web-based program.For example, the concept ID may be generated using WIKI Markup.

In step 1310, the computing device may generate a concept definition forthe new concept. In some aspects, the user may be prompted to provide adefinition. In other aspects (and as previously discussed), thecomputing device may attempt to retrieve a definition from anotherlocation, such as from the web and/or from a business domain databasestoring definitions.

In step 1312, the computing device may generate one or more labels forthe new concept. The labels may identify the context that each conceptmay be used. For example, a security label may indicate that the conceptis used for security purposes as described herein. As another example, abusiness label may indicate that the concept is used for businesspurposes as described herein. Another label may be a logging label. Insome aspects, the logging label may indicate that the concept is usedduring logging by one or more applications.

A user may input the label(s) for each concept. Additionally oralternatively, the label(s) may be automatically determined or generatedby the computing device based on a determination of the appropriatelabel. For example, the computing device may determine that a securityapplication uses the concept and add a security label based on thedetermination. If the security application (or a different application)also uses the concept for data logging, the computing device may add alogging label for the concept. Any number of labels may be added (orremoved) using the foregoing methods.

In step 1314, the computing device may determine whether to generate oneor more mapping dictionaries for the concept. If so, the computingdevice may generate the mapping dictionary in step 1316. The mappingdictionaries may be used to map an application-specific concept name toa domain dictionary name. In some aspects, the mapping dictionaries maybe stored with or be part of the domain dictionary. For example, thedomain dictionary may store multiple concept names for a single conceptID, such as “PartyID,” “Party Identifier,” “Party ID,” “Party_ID,”“PARTY_ID,” and “partyID” for the concept ID XXXX32. One of the conceptnames, such as “PartyID,” may also be identified as the primary conceptname, whereas the remaining concept names may be identified as secondarynames. Alternatively, mapping dictionaries may be generated separatelyfrom the domain dictionary. These separate mapping dictionaries might besimilar to the domain dictionaries, except that they might use theapplication-specific concept name, such as “Party Identifier,” “PartyID,” “Party_ID,” “PARTY_ID,” and “partyID” for the concept ID XXXX32. Bymapping the application-specific concept names to the domain dictionaryconcept names and/or concept IDs, applications may be able to use theirown concept names rather than using concept names used by the domaindictionary. This may be beneficial if, for example, the application is alegacy application having its own logging structure and/or conceptnames.

In step 1318, the computing device may store the concept name, conceptID, definition, label and mapping data, such as in one or more domaindictionary or mapping dictionary. The domain dictionaries may begenerated in two formats: (1) a user-readable format, such as an HTMLtable or other user-readable interface and (2) a machine-readableformat, such as in the form of JavaScript Object Notation for LinkedData (JSON-LD) or any other linked data format, such as ResourceDescription Framework (RDF), Extensible Markup Language (XML), or anyother format utilizing URIs, such as URLs, to link information and/orother format otherwise utilizing context (e.g., semantics) fields.

The user-readable format may include one or more data fields, such asconcept name, concept ID, labels, and definition, and correspondingvalues, as previously discussed. The data fields and values may bestored in a concept repository. An example table is provided herein:

Name Concept ID Label Definition Action_AcctLock /XXXXX1 security,Account being locked out logging Action_AcctMods /XXXXX2 security,Changing of account/role/ logging permissions Action_FailedAccess/XXXXX3 security, Attempts to access data, where as logging they weredenied Action_Login /XXXXX4 security, Login events captured loggingAddressLine1 /XXXXX5 security, Captures if the event record has loggingaccessed/viewed AddressLine1 AddressLine2 /XXXXX6 security, Captures ifthe event record has logging accessed/viewed AddressLine2 AIT /XXXXX7business, Number associated with your logging businesslication from theBusinesslication Inventory Tool (AIT). BusinesslicationNumber /XXXXX8business, COPS businesslication number. logging Will be a legacy number.BusinesslicationSubSectionName /XXXXX9 business, tells us if thebusinesslication has logging subsections/screens/sub- businesslicationsBusinesslicationSubSectionNumber /XXXX10 business, This indicates anbusinesslication logging subsection, or screen, or sub-businesslication. CDNumber /XXXX11 security, Captures if the eventrecord has logging accessed/viewed CDNumber ChallengeResponse /XXXX12security, Captures if the event record has logging accessed/viewedChallengeResponse City /XXXX13 security, Captures if the event recordhas logging accessed/viewed City ClientUniqueIdentifierforMessage/XXXX14 security, Captures if the event record has loggingaccessed/viewed ClientUniqueIdentifierforMessage CreditCardNumber/XXXX15 security, Captures if the event record has loggingaccessed/viewed CreditCardNumber CustomerAccountNumber /XXXX16 security,Captures unique identifier like logging account numberDateTimeAccessed_EndUSer /XXXX17 business, Event Date and Time of endusers logging timezone. DebitCardNumber /XXXX18 security, Captures ifthe event record has logging accessed/viewed DebitCardNumber Email/XXXX19 security, Captures if the event record has loggingaccessed/viewed Email Employee_NBK /XXXX20 business, Associate NBKlogging Employee_PersonNumber /XXXX21 business, Associate Person Numberlogging FirstName /XXXX22 security, Captures if the event record haslogging accessed/viewed FirstName HELOCNumber /XXXX23 security, Capturesif the event record has logging accessed/viewed HELOCNumberIdentification /XXXX24 security, Captures if the event record haslogging accessed/viewed Identification InsurancePolicyNumber /XXXX25security, Captures if the event record has logging accessed/viewedInsurancePolicyNumber IP Address_EndUser /XXXX26 business, IP Address ofthe end user logging performing the action IPAddress /XXXX27 business,IP Address of the machine logging sending the data LastName /XXXX28security, Captures if the event record has logging accessed/viewedLastName MachineName /XXXX29 business, Name of machine loggingMortgageLoanNumber /XXXX30 security, Captures if the event record haslogging accessed/viewed MortgageLoanNumber OtherAccountNumber /XXXX31security, Captures if the event record has logging accessed/viewedOtherAccountNumber PartyID /XXXX32 security, Captures the corporatecustomer logging number/party id of the customer Phone /XXXX33 security,Captures if the event record has logging accessed/viewed PhonePIN_Password /XXXX34 security, Captures if the event record has loggingaccessed/viewed PIN_Password ReceiveDate /XXXX35 security, The date therecord was received logging by COPS RegistrationStatus /XXXX36 business,Status of businesslication. DEV, logging Retired, ProdRegistrationStatus (Subsection /XXXX37 business, Status ofsub-businesslication related) logging SSN_TIN /XXXX38 security, Capturesif the event record has logging accessed viewed SSN State /XXXX39security, Captures if the event record has logging accessed/viewed StateUTCTimeOffset /XXXX40 security, UTC Offset logging ZIP /XXXX41 security,Captures if the event record has logging accessed/viewed ZIP

A corresponding machine-readable domain dictionary may also begenerated, such as in the form of a JSON-LD file, which may be named,for example, “domain1-dictionary.jsonld” (or something similar):

{   ″@context″: {  “domain1”: “http://institution.com/”,  ″Action_AcctLock″: {    ″@id″:″domain1:XXXXX1″, ″@type″: ″@id″    },  ″Action_AcctMods″: {    ″@id″:″domain1:XXXXX2″, ″@type″: ″@id″    },  ″Action_FailedAccess″: {    ″@id″:″domain1:XXXXX3″, ″@type″: ″@id″   },   ″Action_Login″: {    ″@id″:″domain1:XXXXX4″, ″@type″: ″@id″   },   ″AddressLine1″: {    ″@id″:″domain1:XXXXX5″, ″@type″: ″@id″   },   ″AddressLine2″: {    ″@id″:″domain1:XXXXX6″, ″@type″: ″@id″   },   ″AIT″: {    ″@id″:″domain1:XXXXX7″, ″@type″: ″@id″    },  ″ApplicationNumber″: {    ″@id″:″domain1:XXXXX8″, ″@type″: ″@id″    },  ″ApplicationSubSectionName″: {    ″@id″:″domain1:XXXXX9″, ″@type″:″@id″    },   ″ApplicationSubSectionNumber″: {    ″@id″:″domain1:XXXX10″, ″@type″: ″@id″    },   ″CDNumber″: {    ″@id″:″domain1:XXXX11″,″@type″: ″@id″    },   ″ChallengeResponse″: {    ″@id″:″domain1:XXXX12″,″@type″: ″@id″    },   ″City″: {    ″@id″:″domain1:XXXX13″, ″@type″:″@id″    },   ″ClientUniqueIdentifierforMessage″: {   ″@id″:″domain1:XXXX14″, ″@type″: ″@id″    },   ″CreditCardNumber″: {   ″@id″:″domain1:XXXX15″, ″@type″: ″@id″    },  ″CustomerAccountNumber″: {    ″@id″:″domain1:XXXX16″, ″@type″: ″@id″   },   ″DateTimeAccessed_EndUSer″: {    ″@id″:″domain1:XXXX17″,″@type″: ″@id″    },   ″DebitCardNumber″: {    ″@id″:″domain1:XXXX18″,″@type″: ″@id″    },   ″Email″: {    ″@id″:″domain1:XXXX19″, ″@type″:″@id″    },   ″Employee_NBK″: {    ″@id″:″domain1:XXXX20″, ″@type″:″@id″    },   ″Employee_PersonNumber″: {    ″@id″:″domain1:XXXX21″,″@type″: ″@id″    },   ″FirstName″: {    ″@id″:″domain1:XXXX22″,″@type″: ″@id″    },   ″HELOCNumber″: {    ″@id″:″domain1:XXXX23″,″@type″: ″@id″    },   ″Identification″: {    ″@id″:″domain1:XXXX24″,″@type″: ″@id″    },   ″InsurancePolicyNumber″: {   ″@id″:″domain1:XXXX25″, ″@type″: ″@id″    },   ″IP Address_EndUser″:{    ″@id″:″domain1:XXXX26″, ″@type″: ″@id″    },   ″IPAddress″: {   ″@id″:″domain1:XXXX27″, ″@type″: ″@id″    },   ″LastName″: {   ″@id″:″domain1:XXXX28″, ″@type″: ″@id″    },   ″MachineName″: {   ″@id″:″domain1:XXXX29″, ″@type″: ″@id″    },   ″MortgageLoanNumber″:{    ″@id″:″domain1:XXXX30″, ″@type″: ″@id″    },  ″OtherAccountNumber″: {    ″@id″:″domain1:XXXX31″, ″@type″: ″@id″   },   ″PartyID″: {    ″@id″:″domain1:XXXX32″, ″@type″: ″@id″    },  ″Phone″: {    ″@id″:″domain1:XXXX33″, ″@type″: ″@id″    },  ″PIN_Password″: {    ″@id″:″domain1:XXXX34″, ″@type″: ″@id″    },  ″ReceiveDate″: {    ″@id″:″domain1:XXXX35″, ″@type″: ″@id″    },  ″RegistrationStatus″: {    ″@id″:″domain1:XXXX36″, ″@type″: ″@id″   },   ″RegistrationStatus (Subsection related)″: {   ″@id″:″domain1:XXXX37″, ″@type″: ″@id″    },   ″SSN_TIN″: {   ″@id″:″domain1:XXXX38″, ″@type″: ″@id″    },   ″State″: {   ″@id″:″domain1:XXXX39″, ″@type″: ″@id″    },   ″UTCTimeOffset″: {   ″@id″:″domain1:XXXX40″, ″@type″: ″@id″    },   ″ZIP″: {   ″@id″:″domain1:XXXX41″, ″@type″: ″@id″    }   } }

The mapping dictionaries and/or application dictionaries may also begenerated in user-readable format and/or machine-readable format. If anapplication uses its own concept name(s) (e.g., in an applicationdictionary), the application may reference, link, or otherwise associateits concept name(s) with concept name(s) in the domain dictionary via aconcept ID. An example JSON-LD file for an application that uses theconcept name “partyID” (rather than the domain dictionary concept name“PartyID”), which may be named, for example,“application1-dictionaryjsonld” (or something similar), may be asfollows:

{  ″@context″: {   ″@base″: ″http://u.go/domain1-dictionary″,   ″domain1″: ″http://institution.com/″,     ″partyID″: {     ″@id″:″domain1:XXXX32″, ″@type″: ″@id″     }  } }

In this example jsonld file, the application may identify the domaindictionary via a URL “http://u.go/domain1-dictionary,” identify thedomain via a URL “http://institution.com/,” identify the concept name ituses “partyID,” and identify the concept ID “domain1:XXXX32” associatedwith the concept name. As illustrated in the domain dictionary above,the concept ID “domain1:XXXX32” may be associated with concept name“PartyID” used by the domain dictionary. By using this mapping, theapplication may conveniently use one or more of its own terms.

FIG. 14 illustrates block diagrams of example interactions betweenapplications and application dictionaries and/or domain dictionaries. Insome aspects, an application, such as application L.1, may directly usea domain dictionary L 1405. Thus application L.1 might not use anapplication dictionary or a mapping dictionary. In some aspects, anapplication, such as application M.1, may use its own application M.1dictionary. Thus the concept names used by application M.1. might bemapped to the domain dictionary M 1410, as previously discussed.

In some aspects, an application, such as application N.A.1, may useconcept names from its own application N.A.1 dictionary as well conceptnames from a domain dictionary, such as domain N dictionary (Unit B).Thus some of the concept names used by application N.A.1. might bemapped to one or more domain dictionary, such as domain dictionary N1415 and/or domain N dictionary (Unit B). On the other hand, conceptsthat application N.A.1 uses directly from a domain dictionary might notneed to be mapped. As illustrated, the domain dictionary N 1415 may havetwo sub-dictionaries, Unit A and Unit B. Applications may choose to useone or more of these sub-dictionaries.

An application that uses its own dictionary can annotate data elementsin a data log to map elements in the log to concept names used by thedomain dictionary. Thus, an application concept name can be tied to acanonical concept name in the domain dictionary. Accordingly, each timean application concept name is referenced, such as in a data log, thebusiness domain, analytical engines having access to the domaindictionary, or other applications may identify the proper concept namefrom the domain dictionary. Using this mapping technique, analyticalengines may be able to onboard and maintain applications moreconveniently, consume and/or analyze data logs quicker, and generateanalytical reports more quickly.

FIG. 15 is a flowchart of example method steps for generating a logusing one or more dictionaries. In step 1502, an application may receivea request to generate a log, such as in response to an event asillustrated in the table above. For example, a user may issue a commandto generate the log, such as via a user interface on a workstation.Additionally or alternatively, a computing device associated with abusiness domain may send a command to the application to generate thelog. In some aspects, the application may periodically generate logs.

In step 1504, the application may determine whether the application usesan application dictionary. If the application uses an applicationdictionary (step 1504: Yes), it may retrieve the application dictionaryin step 1506. The application may also retrieve a mapping, such as amapping dictionary or file, that maps one or more concept names in theapplication dictionary to one or more concept names in the domaindictionary in step 1506. The application dictionary may be stored, forexample, within the application (or associated database). The mappingmay also be stored, for example, within the application (or associateddatabase), or it may be stored within a particular domain, such as arelated business domain.

In step 1508, the application may retrieve the domain dictionary. Instep 1510, for concept names found in the application dictionary, theapplication may map the application dictionary concept names to aconcept ID that may be stored in the domain dictionary, as previouslydiscussed. In step 1512, for concept names taken from the domaindictionary, the application may directly reference the domain dictionary(rather than generating a mapping). If the application does not use anapplication dictionary for any concepts (step 1504: No), the applicationmay retrieve the domain dictionary in step 1514 and directly referencethe domain dictionary for concepts the application plans to include inthe log.

In step 1516, the application may generate the log using the domaindictionary, the application dictionary, and/or the mapping dictionary orfile. In particular, the log might include several field-value pairsrelated to a particular action. Example actions were previouslyillustrated in the user-readable table previously discussed. Forexample, if a customer of an institution, such as a financialinstitution, attempts to access data, but the access is denied, the logmay include a concept name “Action_FailedAccess” (if the domaindictionary is used) or concept name “Customer_Access_Attempt” with areference to concept ID XXXXX3 (if an application dictionary having theconcept name “Customer_Access_Attempt” is used). The log might alsoindicate the time and date of the access attempt and/or the IP addressof the customer attempting to access the data (e.g., “IPAddress_EndUser” if the domain dictionary is used). Any of the conceptsillustrated in the above table, as well as concepts not illustrated, maybe included in generated logs.

In step 1516, the log may be provided to an analysis system (e.g., ananalytical engine) to process the data. In some aspects, the analysissystem may have access to the domain dictionary. By accessing the domaindictionary and the mapping for application-specific concept names,analysis systems may be able to onboard and maintain applications moreconveniently, consume and/or analyze data logs quicker, and generateanalytical reports more quickly. For example, the analysis systems maysearch and report analytics across multiple applications, such as searchand analytical dashboards, because of the use of common concept IDs.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1. (canceled)
 2. A non-transitory computer-readable medium storingcomputer-readable instructions that, when read by a computing device,cause the computing device to: determine that a data security event or adata logging event occurs at an application running on a computingdomain; in response to determining that the data security event or thedata logging event occurs at the application running on the computingdomain, determine that the application uses a first concept name from anapplication dictionary associated with the application to describe thedata security event or the data logging event; generate an entry for thedata security event or the data logging event and add the entry to adata log for the application running on the computing domain, whereinthe entry includes the first concept name from the applicationdictionary associated with the application; determine that the firstconcept name from the application dictionary corresponds to a secondconcept name from a domain dictionary associated with a plurality ofapplications running on the computing domain; and generate a mapping ofthe first concept name from the application dictionary to the secondconcept name from the domain dictionary associated with the plurality ofapplications running on the computing domain.
 3. The non-transitorycomputer-readable medium of claim 2, wherein generating the mappingcomprises generating a mapping file that identifies the domaindictionary, the first concept name from the application dictionary, anda concept identifier for the data security event or the data loggingevent.
 4. The non-transitory computer-readable medium of claim 3,wherein the mapping file does not identify the second concept name fromthe domain dictionary.
 5. The non-transitory computer-readable medium ofclaim 3, wherein the mapping file comprises a JavaScript Object Notationfor Linked Data (JSON-LD) file.
 6. The non-transitory computer-readablemedium of claim 2, wherein the domain dictionary comprises a pluralityof concept names including the second concept name, and wherein each ofthe plurality of concept names corresponds to a concept identifier. 7.The non-transitory computer-readable medium of claim 6, wherein thedomain dictionary comprises a JavaScript Object Notation for Linked Data(JSON-LD) file.
 8. The non-transitory computer-readable medium of claim2, wherein generating the mapping comprises: associating the firstconcept name from the application dictionary to a concept identifier;and associating the second concept name from the domain dictionary tothe concept identifier.
 9. The non-transitory computer-readable mediumof claim 2, storing computer-readable instructions that, when read bythe computing device, further cause the computing device to: in responseto a determination that a second event occurs at the application,determine that the application uses a third concept name from the domaindictionary to describe the second event; and add a second entry for thesecond event to the data log for the application, wherein the secondentry includes the third concept name from the domain dictionary. 10.The non-transitory computer-readable medium of claim 2, storingcomputer-readable instructions that, when read by the computing device,further cause the computing device to: send the data log to a data loganalysis system, wherein the data log analysis system is capable ofaccessing the domain dictionary.
 11. A method comprising: in response toa determination that an event occurs at an application, determining, bya computing device having a processor and memory, that the applicationuses a first concept name from an application dictionary to describe theevent; adding an entry for the event to a data log for the application,wherein the entry includes the first concept name from the applicationdictionary; and generating a mapping of the first concept name from theapplication dictionary to a second concept name from a domaindictionary, wherein the domain dictionary is different from theapplication dictionary, wherein generating the mapping comprisesgenerating a mapping file that identifies the domain dictionary, thefirst concept name from the application dictionary, and a conceptidentifier for the event, and wherein the mapping file comprises aJavaScript Object Notation for Linked Data (JSON-LD) file.
 12. Themethod of claim 11, wherein the mapping file does not identify thesecond concept name from the domain dictionary.
 13. The method of claim11, wherein the domain dictionary comprises a plurality of concept namesincluding the second concept name, and wherein each of the plurality ofconcept names corresponds to a concept identifier.
 14. The method ofclaim 13, wherein the domain dictionary comprises a JavaScript ObjectNotation for Linked Data (JSON-LD) file.
 15. The method of claim 11,wherein generating the mapping comprises: associating the first conceptname from the application dictionary to the concept identifier; andassociating the second concept name from the domain dictionary to theconcept identifier.
 16. The method of claim 11, further comprising: inresponse to a determination that a second event occurs at theapplication, determining that the application uses a third concept namefrom the domain dictionary to describe the second event; and adding asecond entry for the second event to the data log for the application,wherein the second entry includes the third concept name from the domaindictionary.
 17. The method of claim 11, further comprising: sending thedata log to a data log analysis system, wherein the data log analysissystem is capable of accessing the domain dictionary.
 18. An apparatuscomprising: a processor; and memory storing computer-executableinstructions that, when executed by the processor, cause the apparatusto: in response to a determination that an event occurs at anapplication, determine that the application uses a first concept namefrom an application dictionary to describe the event; add an entry forthe event to a data log for the application, wherein the entry includesthe first concept name from the application dictionary; and generate amapping of the first concept name from the application dictionary to asecond concept name from a domain dictionary, wherein the domaindictionary is different from the application dictionary, whereingenerating the mapping comprises generating a mapping file thatidentifies the domain dictionary, the first concept name from theapplication dictionary, and a concept identifier for the event, andwherein the mapping file comprises a JavaScript Object Notation forLinked Data (JSON-LD) file.
 19. The apparatus of claim 18, wherein themapping file does not identify the second concept name from the domaindictionary.
 20. The apparatus of claim 18, wherein the domain dictionarycomprises a plurality of concept names including the second conceptname, and wherein each of the plurality of concept names corresponds toa concept identifier.
 21. The apparatus of claim 20, wherein the domaindictionary comprises a JavaScript Object Notation for Linked Data(JSON-LD) file.